home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19990422-19990725
/
000304_news@columbia.edu _Tue Jul 20 04:25:11 1999.msg
< prev
next >
Wrap
Internet Message Format
|
1999-07-23
|
3KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id EAA10349
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 20 Jul 1999 04:25:10 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id EAA01531
for kermit.misc@watsun.cc.columbia.edu; Tue, 20 Jul 1999 04:15:44 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: Rok Zevnik <zevnik@asterix.ijs.si>
Subject: Re: set translation input command in Kermit 95?
Date: Tue, 20 Jul 1999 10:10:22 +0200
Organization: Jozef Stefan Institute
Message-ID: <Pine.SUN.3.96.990720095136.21381A-100000@asterix>
To: kermit.misc@columbia.edu
Hello again,
Maybe there's just another problem. That everything which runs on that
host computer is made so that converts these characters in {}[]. And this
is a lot of source to edit. So we have tomake changes on the client side.
Maybe this solution would be useful if I set on client side that
host computer uses cp437 and then with set key command translate outgoing
characters in []{} but this is just half of the sollution because native
signs will be printed alright but on display they won't see them.
Any other solution for the client side? maybe custom character-set?
Lep pozdrav / Best regards,
Rok Zevnik
On 19 Jul 1999, Jeffrey Altman wrote:
> In article <Pine.SUN.3.96.990719112620.20970A-100000@asterix>,
> Rok Zevnik <zevnik@asterix.ijs.si> wrote:
> : Hello,
> :
> : On the host computer (RS/6000, AIX4.2) we have latin2-iso character set
> : and the client (PC, Win95) is using CP1250. But because the terminal which
> : is connected on the host doesn't recognize the iso2 standart we are not
> : allowed to use any of our native characters so we are running a script
> : which converts that characters to '[]{}'. And we would like to see this
> : characters to display correctly as =E8=E6=BE=F0 on our client. The perfect =
> : thing
> : would be set translation input but it isn't supported anymore.=20
> : What are the possible sollutions?
> : =20
> :
> : Lep pozdrav / Best regards,
> :
> : Rok Zevnik
> :
>
> The best solution would be for you to make the script on the host
> conditional based upon the terminal type $TERM so that when you
> are logged in using Kermit which does understand ISO Latin2 for both
> input and output that you can do so.
>
> SET TRANSLATION INPUT was a really bad idea because it allowed you to do
> things such as your script which are incompatible with every terminal.
>
> Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
> The Kermit Project * Columbia University
> 612 West 115th St #716 * New York, NY * 10025
> http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org
>
>